feat[code]: extend DetectedMovingObject with estimated trajectory #752
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
refers to OpenSimulationInterface#751 Extends the DetectedMovingObject with a series of StatePoints to describe an estimated future trajectory. Signed-off-by: Dennis Otte <[email protected]>
|
Comment from OSI Workgroup Other Models:
|
|
ASAM OSI CCB 2025-04-10: A working group is needed to work on this. |
yash-shah-asam
added
the
Broad Discussion
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reference to a related issue in the repository
751
Add a description
This proposal adds repeated StatePoints to the message DetectedMovingObject to describe an estimated future trajectory of this entity.
Some questions to ask:
What is this change?
What does it fix?
Is this a bug fix or a feature? Does it break any existing functionality or force me to update to a new version?
How has it been tested?
Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:
If you can’t check all of them, please explain why.
If all boxes are checked or commented and you have achieved at least one positive review, you can assign the label ReadyForCCBReview!
This pull request is planned to be discussed in the Subgroup Other Models & Harmonization Joint Meeting 17.12.2023.